-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ListOffsetsRequest should only be sent to the leader replica (CI) #4754
Conversation
@emasab do you think this PR could be merged soon? I saw there were some CI issues on previous iterations of this PR but this one looks green |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -111,6 +110,11 @@ static void do_test_offset_reset(const char *auto_offset_reset) { | |||
else | |||
test_consumer_poll(auto_offset_reset, c, 0, 1, 0, msgcnt, NULL); | |||
|
|||
/* send another batch of messages to ensure the consumer isn't stuck */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a good idea to expand on why exactly we add this and why the consumer was getting stuck, alternatively, we can provide the issue # . Without that, it'll be a bit difficult for future readers.
CHANGELOG.md
Outdated
* Fix segfault when using long client id because of erased segment when using flexver. (#4689) | ||
* Update bundled lz4 (#4726) | ||
* Fix segfault when using long client id because of erased segment when using flexver. (#4689) | ||
* Fix for a loop of ListOffset requests, happening in a Fetch From Follower |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix changelog for this to be in 2.5.1
🎉 All Contributor License Agreements have been signed. Ready to merge. |
4d463c9
to
89369d8
Compare
89369d8
to
7d09ee5
Compare
Continuation of #4616 from an internal branch due to CI issues